Rollback the XCO Upgrade

Rollback the XCO upgrade when there is a upgrade failure. After the rollback, XCO operates in the previous state by canceling the upgrade.

About this task

Follow this procedure to rollback the XCO upgrade.

Note

Ensure that the minimum EFA version is 3.1.0 and above and the minimum SLX version is 20.4.2 and above.
Ensure that the minimum available disk space is 2 GB on each SLX TPVM partition. Log in to SLX as a root user and run the following command:
```
[root@SLX-1]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        16G  4.6G   11G  32% /
```

Procedure

Deploy XCO with rollback.

efa deploy nographics with-rollback slx-peer-ip <ip-address> slx-peer-user <user name> slx-peer-password <password>

When you use the rollback option, the following parameters are required:

slx-peer-ip - SLX IP, which hosts peer TPVM
slx-peer-user - SLX user, which hosts peer TPVM
slx-peer-password - SLX password, which hosts peer TPVM

Example

The following is an example of a deployment with rollback option:

efa deploy nographics with-rollback slx-peer-ip 10.20.54.62 slx-peer-user admin slx-peer-password password

Step 1: Get IP Address assigned to TPVM to deploy EFA  10.20.63.128.
Step 2: Checking for EFA packages in /efaboot directory
1. /efaboot/efa-3.4.0-32.tar.gz
2. /efaboot/efa-3.4.0-31.tar.gz
Enter option: 1
**********************************************************************
*                 ! ! ! WARNING ! ! !                                *
*  Proceeding with Extreme Fabric Automation deployment              *
*       1. Do not reboot device(s) or TPVM(s)                        *
*       2. Do not toggle management port on device(s) or TPVM(s)     *
*       3. Avoid CTRL+C on the installer window                      *
**********************************************************************
Ensuring TPVM 10.20.63.129 is deployed on remote SLX 10.20.54.62... done.
Ensuring EFA supports this rollback procedure... done.
Putting EFA into quiescent state............... done.
Stopping database on standby TPVM.... done.
Stopping database on active TPVM.... done.
Taking snapshot of active TPVM... done.
Taking snapshot of standby TPVM... done.
Starting database on active TPVM.................. done.
Starting database on standby TPVM.... done.
Waiting for EFA to start.......................... done.
Completed EFA install preparation.
Copying EFA package efa-3.4.0-32.tar.gz to TPVM 10.20.63.128... done.
Extracting EFA package efa-3.4.0-32.tar.gz on TPVM 10.20.63.128... done.
Starting EFA installer.
Step 3: Checking for EFA Stack...
Previous Stack found
Are you sure you want to re-deploy EFA? (yes/no)
no
Do you wish to restart the install? (yes/no)
no
Preserving EFA supportsave... done.
Powering off standby TPVM... done.
Powering off active TPVM... done.
Reverting to saved EFA state on active... done.
Waiting for TPVM to boot on active....................... done.
Reverting to saved EFA state on standby... done.
Copying EFA supportsave back to TPVM... done.
Waiting for EFA to start................................................ done.
Completed EFA revert procedure.
EFA revert succeeded.
EFA deployment discontinued or failed.
Spine1#

The following is an example of an upgrade failure with rollback option:

Spine1# efa deploy non-interactive with-rollback slx-peer-ip 10.20.54.62 slx-peer-user admin slx-peer-password password multi-node package /efaboot/efa-3.4.0-32.tar.gz
Initializing...
**********************************************************************
* ! ! ! WARNING ! ! ! *
* Proceeding with Extreme Fabric Automation deployment *
* 1. Do not reboot device(s) or TPVM(s) *
* 2. Do not toggle management port on device(s) or TPVM(s) *
* 3. Avoid CTRL+C on the installer window *
**********************************************************************
Ensuring TPVM 10.20.63.129 is deployed on remote SLX 10.20.54.62... done.
Ensuring EFA supports this rollback procedure... done.
Putting EFA into quiescent state............... done.
Stopping database on standby TPVM.... done.
Stopping database on active TPVM.... done.
Taking snapshot of active TPVM... done.
Taking snapshot of standby TPVM... done.
Starting database on active TPVM.................. done.
Starting database on standby TPVM.... done.
Waiting for EFA to start...................... done.
Completed EFA install preparation.
Copying EFA package efa-3.4.0-32.tar.gz to TPVM 10.20.63.128... done.
Extracting EFA package efa-3.4.0-32.tar.gz on TPVM 10.20.63.128... done.
Starting EFA installer.
Checking for EFA Stack...
Deployment mode is upgrade
Verifying connectivity to 10.20.63.129...
You have entered:
- to redeploy EFA at version 3.4.0 build 32
- with peer 10.20.63.129
- and VIP 10.20.63.127
- with additional HA health ping check IP(s) 10.20.54.63,10.20.54.64
Making backup
Removing legacy EFA installation
Stopping EFA services
Undeploying EFA application...
Undeploying ecosystem services
Undeploying core services
Removed current application deployment successfully.
Removing EFA container images
Removing container images on 10.20.63.128 10.20.63.129...
Removing EFA OS services
Removing k3s container orchestration
Removing database
Removing cluster filesystem
Removing keepalived for cluster virtual IP
Removing database sync tools
Removing EFA services and utilities
Proceeding with new EFA installation
Verifying system requirements
Verifying system requirements on all nodes
Ensuring networking components are ready
Installing software dependencies
Started installing helm
Installing database migrate client
Installing glusterfs filesystem software
Installing glusterfs 7.2...
GlusterFS Installation Success
Creating clustered filesystem
Configuring glusterfs volumes
Mounting efa volumes for replication to start
Mounting gluster units
Done with mounting of glusterfs efa volumes on nodes
Completed configuring glusterfs
Setting up EFA database
Installing and configuring mariadb server for HA...
Installing perl dependency for database use
Installing database client
Installing database server
Installing mariadb 10.4 server...
MariaDB 10.4 Installation Success
Configuring database server
Failed.
Failed.
Please wait while supportsave runs...
Supportsave complete - /apps/efa_logs/efa_2023-08-26T11-26-40.185.logs.zip
46.016172224s
Preserving EFA supportsave... done.
Powering off standby TPVM... done.
Powering off active TPVM... done.
Reverting to saved EFA state on active... done.
Waiting for TPVM to boot on active............. done.
Reverting to saved EFA state on standby... done.
Copying EFA supportsave back to TPVM... done.
Waiting for EFA to start................................................... done.
Completed EFA revert procedure.
EFA revert succeeded.
EFA deployment discontinued or failed.
Spine1#